<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Language" content="en-us">
  <meta http-equiv="Content-Type"
 content="text/html; charset=windows-1252">
  <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
  <meta name="ProgId" content="FrontPage.Editor.Document">
  <title>Test Pass Four</title>
</head>
<body>
<h1>Test Pass Four: JDT UI, JDT Text, Platform Compare, Platform Text,
and Platform Search</h1>
<h3>Testers: Martin, Dani, Markus, David, Tobias, Tom, Dirk</h3>
<h2>Goal</h2>
<ul>
  <li>
  Find stop-ship bugs
			before shipping Eclipse 3.1.
	
The only things
			that can stop us from shipping now are:
<ul>
		<li>
		Eclipse won't start</li>
		<li>
		Deadlocks, Hungs, ...</li>
		<li>
		Crash</li>
		<li>
		Lost work; data destroyed, corrupted or lost</li>
		<li>
		Severe memory leaks</li>
		<li>
		Severe performance regression
		</li>
	</ul>
	</li>
	<li>Test areas that might got broken by bug fixes done in RC3</li>
	<li>Test Java 5.0 functionality. Whenever you create some test code
please use 5.0 language features whenever possible. For example add a
type parameter to every new class, ...<font color="#000000"></font></li></ul>
<h2>Setup / Introduction</h2>
<h3><span style="font-weight: bold;">Build</span></h3>
<ul>
	<li><a
		href="http://download.eclipse.org/eclipse/downloads/drops/S-3.1RC3-200506171618/index.php">eclipse-SDK-3.1RC3</a></li>
</ul>
<h3>Platforms</h3>
<ul>
  <li>Linux-GTK FedoraCore (Tom)</li>
  <li>Windows XP (all others test)</li>
</ul>

<h2>3.1 RC3 items</h2>
<h4>Bug verification (all)</h4>
<ul>
  <li>Verify ALL bugs fixed during RC1 (<a
 href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=JDT&amp;component=Text&amp;component=UI&amp;target_milestone=3.1+RC3&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">JDT/UI
&amp; JDT/Text</a>, <a
 href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=Platform&amp;component=Text&amp;target_milestone=3.1+RC3&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform/Text</a>,<a
 href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;product=Platform&amp;component=Search&amp;target_milestone=3.1+RC3&amp;long_desc_type=allwordssubstr&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=RESOLVED&amp;emailtype1=substring&amp;email1=&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">Platform/Search</a>).</li>
</ul>
<h4>Navigation to package declaration in Java editor (Dirk, Markus FAQ; Dani)</h4><ul>
	<li>test from Package Explorer and Outline view</li>
	<li>test using various package names</li>
	<li>
	<p>add a comment before the package declaration which contains the
	package name (test using traditional, single line and Javadoc comment) and test that navigation still works correctly</p>
	</li>
</ul>
<h4>File Associations, Content Types and opening of editors (Martin, Dani FAQ: Dani)</h4>
<ul>
	<li>test that other editors can be bound to such files and appear in
'Open With'</li>
	<li>test that other editors can be set as the default editor</li>
	<li>add a new association for &quot;*.java&quot; to a plugin.xml and
verify that it appears and that the Java editor is still used as default editor for opening *.java files</li>
	<li>declare above association as default and verify that the Java editor
is still the default editor for opening *.java files</li>
</ul>
<h4>Typing (Markus, David, FAQ: Dani)</h4>
<ul>
	<li>stress indent command (Ctrl+I) in the Java editor</li>
	<li>test move/copy lines </li>
</ul>
<h4>Code Assist (must be tested on all Platforms, including Linux-Motif)
 (Tom, Andre, Tobias FAQ: Dani)</h4>
<ul>
	<li>performance: test if performance is acceptable</li>
	<li> initial list</li>
	<li>narrowing down the list while typing</li>
</ul>

<h4>New project wizard (Tobias, David FAQ: Martin)</h4>
<ul>
	<li>Test the JDK compliance capability of the first page</li>
</ul>
<h4>Java compare (Dirk, Martin FAQ: Dirk/Andre)</h4>
<ul>
	<li>Test comparing Java files with repository content</li>
	<li>Test comparing Outgoing change with repository content.<br>
	<br>For both items make sure that the structure compare pane in the upper right corner looks OK.</li>
</ul>
<h4>Quick type hierarchy (David, Tom FAQ. Martin)</h4>
<ul>
	<li>stress the quick type hierarchy. Make sure that it shows the same result as the type hierarchy in locked mode.</li>
	<li>be aware of bug <a
		href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=100734">100734</a> in the context of generics.</li>
</ul>

<h4>Overriden method indicator (Dani, Tobias FAQ: Martin)</h4>
<ul>
	<li>test overriden method indicator for
	<ul>
		<li>classes extending classes</li>
		<li>classes implementing interfaces and annotations</li>
		<li>enums implementing intefaces and annotations</li>
	</ul>
	</li>
</ul>
<h2>Realize a project (everybody)</h2>
<p>When done with your assigned items from above start realizing whatever &quot;small&quot; project you want. Setup new projects, adjust preferences settings to your normal programming style. Implement the project using J2SE 5.0 features. The goal is to test functionality not covered by your daily developement.</p></body>
</html>
